Skip to content

Adds instructions to run E2E tests#83

Merged
JyotinderSingh merged 2 commits intomainfrom
readme-tests
Mar 9, 2026
Merged

Adds instructions to run E2E tests#83
JyotinderSingh merged 2 commits intomainfrom
readme-tests

Conversation

@JyotinderSingh
Copy link
Collaborator

Adds readme instructions to run e2e tests locally.

@gemini-code-assist
Copy link
Contributor

Summary of Changes

Hello, I'm Gemini Code Assist1! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request significantly improves the developer experience by documenting the process for running End-to-End (E2E) tests. By providing clear, step-by-step instructions, including prerequisites and environment configurations, it enables contributors to more easily set up and execute these critical tests against a GKE cluster, fostering better code quality and a more efficient development workflow.

Highlights

  • E2E Test Documentation: Added comprehensive instructions for running End-to-End (E2E) tests locally within the contributing.md file.
  • Detailed Setup Guide: Included prerequisites, required environment variables, and command examples for executing E2E tests against a GKE cluster.

🧠 New Feature in Public Preview: You can now enable Memory to help Gemini Code Assist learn from your team's feedback. This makes future code reviews more consistent and personalized to your project's style. Click here to enable Memory in your admin console.

Changelog
  • docs/contributing.md
    • Updated the 'Testing' section to explicitly separate unit tests from E2E tests.
    • Introduced a new subsection dedicated to E2E tests, detailing prerequisites such as GCP project, Google Cloud SDK authentication, and GKE credentials.
    • Documented required environment variables like E2E_TESTS, KERAS_REMOTE_PROJECT, KERAS_REMOTE_ZONE, and KERAS_REMOTE_CLUSTER.
    • Provided command examples for running all E2E tests and specific test files, along with a tip for debugging.
Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

Feature Command Description
Code Review /gemini review Performs a code review for the current pull request in its current state.
Pull Request Summary /gemini summary Provides a summary of the current pull request in its current state.
Comment @gemini-code-assist Responds in comments when explicitly tagged, both in pull request comments and review comments.
Help /gemini help Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for GitHub and other Google products, sign up here.

You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.

Footnotes

  1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution.

Copy link
Contributor

@gemini-code-assist gemini-code-assist bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Code Review

This pull request adds clear and helpful instructions for running the end-to-end tests locally. The changes are well-structured, detailing prerequisites, environment variables, and example commands. I have one suggestion to improve the clarity of the gcloud command by linking the placeholders to the environment variables defined in the document.

Note: Security Review has been skipped due to the limited scope of the PR.

Co-authored-by: gemini-code-assist[bot] <176961590+gemini-code-assist[bot]@users.noreply.github.com>
@JyotinderSingh JyotinderSingh merged commit f9b4e79 into main Mar 9, 2026
4 checks passed
@JyotinderSingh JyotinderSingh deleted the readme-tests branch March 9, 2026 20:55
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants